home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 3. _G_a_l_i_l_e_o _V_i_d_e_o, _I_n_d_i_g_o_2 _V_i_d_e_o _a_n_d _I_n_d_y _V_i_d_e_o _I_s_s_u_e_s _a_n_d
- _W_o_r_k_a_r_o_u_n_d_s
-
- Please refer to the _g_a_l_i_l_e_o(_7) man page, which is obtained
- from the _g_a_l_i_l_e_o._m_a_n._p_a_g_e_s subsystem.
-
- Using the _m_e_m_t_o_v_i_d trigger option (-t) may appear confusing.
- The first frame will be continuously output to video until
- the trigger is detected. After that point, the first frame
- is again output followed by the subsequent frames.
-
- When triggering output of a single frame, it may appear as
- if the trigger has been ignored and the frame output. This
- is not the case. After the trigger is detected, the frame
- will be output again.
-
- For customers which have Galileo 1.1, (see _h_i_n_v(_1_M)), an
- extra button control will be available within videopanel,
- (see _v_i_d_e_o_p_a_n_e_l(_1)). This button control can be activated
- only when in genlock sync mode with CCIR timing. It should
- be enabled for digital output using the Galileo 601 Video
- option for highest performance.
-
- Dual head graphics is now supported. Two XL graphics boards
- can be installed in the Indigo2. One Galileo or Indigo2
- Video board may be connected to one of the XL boards. Only
- one video board is currently supported.
-
- Xlock with the display mode set to "pop" is not recommended
- to run on Galileo with the Elan/XS, Extreme/XZ graphics.
- This operation causes spurious pixels splatter on the video
- output.
-
- "VL: failed allocation of resource or memory" error message
- is generated on Galileo, Indigo R4K with 16Mbytes memory
- configuration while running vidtomem to capture a full frame
- of RGB data or running memtovid to display a full frame of
- YUV422 data. There is not enough memory to transfer video
- data with software color space conversion.
-
- The Video Library, (VL), control for VL_FREEZE is not
- supported on memory nodes.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-